6.8
MEDIUM CVSS 3.1
CVE-2026-9617
PostgreSQL Anonymizer: malicious column name allows SQL injection via anon.k_anonymity() function
Description

PostgreSQL Anonymizer contains a vulnerability that allows a user to gain superuser privileges by creating a table and placing malicious code inside a column identifier. If a superuser calls the k-anonymity function, the malicious code is executed with superuser privileges. The risk is higher with PostgreSQL 14 or with instances upgraded from PostgreSQL 14 or a prior version. With PostgreSQL 15 and later, the creation permission on the public schema is revoked by default and this exploit can only be achieved by a user who was explicitly granted the CREATE TABLE privilege. The problem is resolved in PostgreSQL Anonymizer 3.1.0 and further versions

INFO

Published Date :

May 27, 2026, 2:17 p.m.

Last Modified :

May 27, 2026, 2:54 p.m.

Remotely Exploit :

Yes !

Source :

f86ef6dc-4d3a-42ad-8f28-e6d5547a5007
Affected Products

The following products are affected by CVE-2026-9617 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

No affected product recoded yet

CVSS Scores
The Common Vulnerability Scoring System is a standardized framework for assessing the severity of vulnerabilities in software and systems. We collect and displays CVSS scores from various sources for each CVE.
Score Version Severity Vector Exploitability Score Impact Score Source
CVSS 3.1 MEDIUM f86ef6dc-4d3a-42ad-8f28-e6d5547a5007
CVSS 3.1 MEDIUM MITRE-CVE
Solution
Upgrade PostgreSQL Anonymizer to version 3.1.0 or later to fix privilege escalation.
  • Upgrade PostgreSQL Anonymizer to 3.1.0 or later.
  • Review CREATE TABLE privileges on public schema.
  • Remove unnecessary CREATE TABLE privileges.
References to Advisories, Solutions, and Tools

Here, you will find a curated list of external links that provide in-depth information, practical solutions, and valuable tools related to CVE-2026-9617.

URL Resource
https://gitlab.com/dalibo/postgresql_anonymizer/-/issues/640
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2026-9617 is associated with the following CWEs:

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2026-9617 vulnerability anywhere in the article.

The following table lists the changes that have been made to the CVE-2026-9617 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • New CVE Received by f86ef6dc-4d3a-42ad-8f28-e6d5547a5007

    May. 27, 2026

    Action Type Old Value New Value
    Added Description PostgreSQL Anonymizer contains a vulnerability that allows a user to gain superuser privileges by creating a table and placing malicious code inside a column identifier. If a superuser calls the k-anonymity function, the malicious code is executed with superuser privileges. The risk is higher with PostgreSQL 14 or with instances upgraded from PostgreSQL 14 or a prior version. With PostgreSQL 15 and later, the creation permission on the public schema is revoked by default and this exploit can only be achieved by a user who was explicitly granted the CREATE TABLE privilege. The problem is resolved in PostgreSQL Anonymizer 3.1.0 and further versions
    Added CVSS V3.1 AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H
    Added CWE CWE-89
    Added Reference https://gitlab.com/dalibo/postgresql_anonymizer/-/issues/640
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.